Enhanced reboot command

ABSTRACT

A method and system allows a computer system to perform a network reboot in response to an enhanced reboot command. The computer system receives a command to load an operating system and interprets the command to determine whether a physical machine or a virtual machine is to be rebooted. In response to a determination that the command indicates the use of a network option, the computer system loads the operating system from a networked server, and perform rebooting according to the interpreted command with the use of the operating system.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.12/916,980, filed on Nov. 1, 2010, the entirety of which is incorporatedherein by reference.

TECHNICAL FIELD

Embodiments of the present invention relate to a computer system, andmore specifically, to network rebooting a computer system

BACKGROUND

Network booting (or “network rebooting”) refers to the booting (orrebooting) of a computer over a network, using the operating system (OS)stored on the storage of a server. An initial set of software is loadedfrom a server over a network. The server from which to load the initialsoftware and the OS is usually found by broadcasting or multicasting arequest. This initial software contains enough data to take control ofthe rebooting process and to load the OS over the network.

In most current computer systems, if a user wants to command a computerto perform a network reboot, he needs to wait for the Basic Input/OutputSystem (BIOS) initialization to start and then enter a special command(e.g., F12) during the rebooting process. The special command directsthe computer to reboot from the network. The need of human interactionmakes it difficult to automate the network rebooting process.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, and can be more fully understood with reference to thefollowing detailed description when considered in connection with thefigures in which:

FIG. 1 is a block diagram of a network architecture in which someembodiments of the invention may be implemented.

FIG. 2 is a block diagram of one embodiment of a computer system capableof performing a network reboot.

FIG. 3 is a flow diagram of one embodiment of a method for rebooting acomputer system.

FIG. 4 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system.

DETAILED DESCRIPTION

Described herein is a method and system for performing a network rebootin response to an enhanced reboot command. In one embodiment, a computersystem receives a command to load an operating system and interprets thereboot command to determine whether a physical machine or a virtualmachine is to be rebooted. In response to a determination that thecommand indicates the use of a network option, the computer system loadsthe operating system from a networked server, and perform rebootingaccording to the interpreted command with the use of the operatingsystem.

According to one embodiment of the invention, a user (e.g., a systemadministrator) may send a reboot command that includes a flag (e.g., a“-net” flag) in the same command line to indicate the use of a networkoption. Upon receiving the reboot command, the computer system mayattempt to perform a network boot (that is, booting from a networkedserver) instead of trying to boot from a local disk. If no network isavailable to the computer system, the computer system may try to bootfrom a local disk. The reboot command described herein provides greatsimplicity and flexibility in allowing a user to determine, at eachreboot time, whether to perform a network boot. A network reboot can beperformed at the discretion of the user without the user sending anothercommand (e.g., F12) during the reboot process. The user also does notneed to modify a stored reboot priority list each time he wishes toforce a network reboot. When the reboot command indicates the use of thenetwork option, the computer system can perform a network reboot withoutfirst checking the stored reboot priority list.

In the descriptions herein, the terms “booting” and “rebooting” may beused interchangeably to describe a process for loading an operatingsystem and starting a computer system. The computer system herein may bea physical computer, or a virtual machine that runs on a host computer.

Embodiments of the present invention allow a user to command a computerto network reboot in a single command, without the need for the user toenter another command during the rebooting process.

In the following description, numerous details are set forth. It will beapparent, however, to one skilled in the art, that the present inventionmay be practiced without these specific details. In some instances,well-known structures and devices are shown in block diagram form,rather than in detail, in order to avoid obscuring the presentinvention.

FIG. 1 is a block diagram that illustrates an embodiment of a computersystem 100 that is coupled to one or more servers 120 via a network 125.The network 125 may be a private network (e.g., a local area network(LAN), a wide area network (WAN), intranet, etc.) or a public network(e.g., the Internet). Each of the computer system 100 and the servers120 may be a computer (e.g., a server, a workstation, a personalcomputer (PC), a laptop, etc.), a mobile phone, a hand-held computingdevice, a game station, a personal digital assistant (PDA), etc.

In one embodiment, the computer system 100 may be coupled to an I/Odevice 170 (e.g., a keyboard, a display screen, etc.), through which toreceive commands from a user (e.g., a system administrator).

In one embodiment, at least one of the servers 120 is coupled to a datastorage 180, which may include mass storage devices, such as magnetic oroptical storage based disks, tapes or hard drives. The data storage 180may store an operating system (OS) 185. In one embodiment, the computersystem 100 can load a copy of the OS 185 over the network 125 and storesthe copy locally as an OS 160.

According to one embodiment of the present invention, the computersystem 100 comprises a reboot manager 150 to manage the rebootingprocess of the computer system 100. Rebooting refers to the operationsof reloading the software (including the OS) that runs on a computer.The reboot manager 150 responds to a reboot command from a user to loadan OS and to restart the computer system 100. In one embodiment, thereboot command includes a flag (e.g., “-net”) in a single command. Theflag indicates a network option is to be used to load an OS from one ofthe servers 120.

In one embodiment, the reboot manager 150 may additionally oralternatively manage the rebooting process of one or more virtualmachines that are hosted by the computer system 100. Each virtualmachine runs a guest operating system (OS). The virtual machines mayhave the same or different guest operating systems, such as MicrosoftWindows®, Linux®, Solaris®, Mac® OS, etc. The computer system 100 mayrun a hypervisor to emulate underlying host hardware, making the use ofthe virtual machine transparent to the guest OS and the user of thecomputer system 100. The hypervisor may also be known as a virtualmachine monitor (VMM) or a kernel-based hypervisor. In some embodiments,the hypervisor may be part of the host OS. In one embodiment, the rebootmanager 150 responds to a reboot command (e.g., a reboot command thatincludes the “-net” flag) to reboot one of the virtual machines usingthe OS loaded from one of the networked servers 120.

FIG. 2 is a block diagram that illustrates an embodiment of the computersystem 100 in more detail. In this embodiment, the computer system 100uses a command interpreter 210 to interpret the commands received by thecomputer system 100; e.g., through the I/O device 170 of FIG. 1. In oneembodiment, when a reboot command is received, the command interpreter210 may determine whether the command includes a flag that indicates theuse of the network option. The command interpreter 210 then passes theinterpreted command to the reboot manager 150. If the network option isto be used, the reboot manager 150 looks up a server address 240 inmemory. In one embodiment, the server address 240 is the InternetProtocol (IP) address of the server 120 from which an OS is to beloaded. The IP address may be stored and configured by a systemadministrator. In another embodiment, the IP address is found by thecomputer system 100 sending a multicasting or broadcasting request toall of the servers 120.

In one embodiment, if the network option is not to be used, the rebootmanager 150 looks up the reboot priority list 250 to determine fromwhich location an OS is to be loaded. The reboot priority list 250 maybe stored and configured by a system administrator when the computersystem is in operation. In an alternative embodiment, the reboot manager150 may use a default location (e.g., a local hard drive) to load the OSwithout looking up the reboot priority list 250. The computer system 100also uses a Basic Input/Output System (BIOS) 220 to store bootstrappingsoftware in a non-volatile memory (e.g., read-only memory (ROM)). TheBIOS 220 loads the OS from the location indicated by the reboot manager150. The computer system 100 then restarts using the newly-loaded OS.

In one embodiment, a user can set a boot order in the reboot prioritylist 250. For example, the user may enter the command “reboot -bootpnet, cd, hda, hdb” to set the boot order to be: network, CD-ROM, HardDisk (HD) -a, HD -b. In response to the command, the reboot manager 150updates the reboot priority list 250 accordingly.

FIG. 3 is a flow diagram illustrating one embodiment of a method 300 forrebooting a computer system using a network option. The method 300 maybe performed by a computer system 400 of FIG. 4 that may comprisehardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (e.g., instructions run on a processingdevice), or a combination thereof. In one embodiment, the method 300 isperformed by the computer system 100 of FIG. 1 and FIG. 2.

Referring to FIG. 3, in one embodiment, the method 300 begins when thecomputer system 100 receives a reboot command from a user (block 310).If the computer system 100 hosts one or more virtual machines, thereboot command may specify one of the virtual machines, or the physicalcomputer system 100, as the “machine” to be rebooted. The computersystem 100 interprets the command (block 320), and determines, withoutany user interaction, whether a physical machine or a virtual machine isto be rebooted, and whether the command indicates that a network optionis to be used (block 330) (e.g., by checking whether the reboot commandincludes a “-net” flag). If the network option is to be used, thecomputer system 100 identifies, without any user interaction, theaddress of a networked server from which the OS is to be loaded (block340). If the network option is not to be used, the computer system 100identifies, without any user interaction, a location from which to loadthe OS based on the reboot priority list 250 (FIG. 2) (block 350) or adefault location. The computer system 100 then shuts down all runningprograms on the physical machine or the virtual machine to be rebooted(block 360). The computer system 100 passes control to the BIOS 220,which uses a bootloader to load an OS from the identified location(block 370). The computer system 100 then performs rebooting of thephysical machine or the command-specified virtual machine using thenewly-loaded OS (block 380).

In one embodiment, the reboot command may include the “-net” option whenno network is available to the computer system 100. In this scenario,the computer system 100 may first attempt to load the OS from a networklocation. When the computer system 100 detects that a network does notexist, the computer system 100 will load an OS according to the rebootpriority list 250 or a default location.

FIG. 4 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system 400 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine may be connected (e.g., networked) to othermachines in a Local Area Network (LAN), an intranet, an extranet, or theInternet. The machine may operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a server, a network router, switch or bridge, or any machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine. Further, while only asingle machine is illustrated, the term “machine” shall also be taken toinclude any collection of machines (e.g., computers) that individuallyor jointly execute a set (or multiple sets) of instructions to performany one or more of the methodologies discussed herein.

The exemplary computer system 400 includes a processing device 402, amain memory 404 (e.g., read-only memory (ROM), flash memory, dynamicrandom access memory (DRAM) such as synchronous DRAM (SDRAM) or RambusDRAM (RDRAM), etc.), a static memory 406 (e.g., flash memory, staticrandom access memory (SRAM), etc.), and a secondary memory 418 (e.g., adata storage device), which communicate with each other via a bus 430.

The processing device 402 represents one or more general-purposeprocessing devices such as a microprocessor, central processing unit, orthe like. More particularly, the processing device 402 may be a complexinstruction set computing (CISC) microprocessor, reduced instruction setcomputing (RISC) microprocessor, very long instruction word (VLIW)microprocessor, processor implementing other instruction sets, orprocessors implementing a combination of instruction sets. Theprocessing device 402 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor, or the like. The processing device 402 is configuredto execute reboot management logic 422 for performing the operations andsteps discussed herein.

The computer system 400 may further include a network interface device408. The computer system 400 also may include a video display unit 410(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), analphanumeric input device 412 (e.g., a keyboard), a cursor controldevice 414 (e.g., a mouse), and a signal generation device 416 (e.g., aspeaker).

The secondary memory 418 may include a machine-readable storage medium(or more specifically a computer-readable storage medium) 431 on whichis stored one or more sets of instructions (e.g., reboot managementlogic 422) embodying any one or more of the methodologies or functionsdescribed herein (e.g., the reboot manager 150 of FIGS. 1 and 2). Thereboot management logic 422 may also reside, completely or at leastpartially, within the main memory 404 and/or within the processingdevice 402 during execution thereof by the computer system 400; the mainmemory 404 and the processing device 402 also constitutingmachine-readable storage media. The reboot management logic 422 mayfurther be transmitted or received over a network 420 via the networkinterface device 408.

The machine-readable storage medium 431 may also be used to store thereboot management logic 422 persistently. While the machine-readablestorage medium 431 is shown in an exemplary embodiment to be a singlemedium, the term “machine-readable storage medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more sets of instructions. The term “machine-readable storagemedium” shall also be taken to include any medium that is capable ofstoring or encoding a set of instructions for execution by the machinethat causes the machine to perform any one or more of the methodologiesof the present invention. The term “machine-readable storage medium”shall accordingly be taken to include, but not be limited to,solid-state memories, and optical and magnetic media.

The computer system 400 may additionally include reboot managementmodules 428 for implementing the functionalities of the reboot manager150 of FIGS. 1 and 2. The module 428, components and other featuresdescribed herein (for example in relation to FIG. 1) can be implementedas discrete hardware components or integrated in the functionality ofhardware components such as ASICS, FPGAs, DSPs or similar devices. Inaddition, the module 428 can be implemented as firmware or functionalcircuitry within hardware devices. Further, the module 428 can beimplemented in any combination of hardware devices and softwarecomponents.

Some portions of the detailed descriptions which follow are presented interms of algorithms and symbolic representations of operations on databits within a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “receiving”, “interpreting”,“loading”, “causing”, or the like, refer to the action and processes ofa computer system, or similar electronic computing device, thatmanipulates and transforms data represented as physical (electronic)quantities within the computer system's registers and memories intoother data similarly represented as physical quantities within thecomputer system memories or registers or other such information storage,transmission or display devices.

Embodiments of the present invention also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, or it may comprise a generalpurpose computer system selectively programmed by a computer programstored in the computer system. Such a computer program may be stored ina computer readable storage medium, such as, but not limited to, anytype of disk including optical disks, CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic disk storage media, optical storage media, flashmemory devices, other type of machine-accessible storage media, or anytype of media suitable for storing electronic instructions, each coupledto a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct a more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear as set forth in thedescription below. In addition, the present invention is not describedwith reference to any particular programming language. It will beappreciated that a variety of programming languages may be used toimplement the teachings of the invention as described herein.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other embodiments will beapparent to those of skill in the art upon reading and understanding theabove description. Although the present invention has been describedwith reference to specific exemplary embodiments, it will be recognizedthat the invention is not limited to the embodiments described, but canbe practiced with modification and alteration within the spirit andscope of the appended claims. Accordingly, the specification anddrawings are to be regarded in an illustrative sense rather than arestrictive sense. The scope of the invention should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

What is claimed is:
 1. A method comprising: receiving, by a processingdevice, a command to load an operating system, wherein the operatingsystem to be loaded is a host operating system for a physical machine ora guest operating system for a virtual machine; determining whether thecommand includes a flag set to a network option; in response to adetermination that the command includes the flag set to the networkoption, loading the operating system as the host operating system or theguest operating system from a networked server to the processing device;in response to a determination that the command does not include theflag set to the network option, loading the operating system from alocation other than the networked server to the processing device; andcausing rebooting to be performed according to the command with the useof the operating system.
 2. The method of claim 1, wherein loading theoperating system from a location other than the networked server to theprocessing device comprises: determining the location based on a rebootpriority list accessible by the processing device.
 3. The method ofclaim 1, wherein loading the operating system comprises: identifying anetwork address of the networked server.
 4. The method of claim 1,further comprising: receiving, by the processing device, a rebootcommand that includes a reboot priority list; and storing the rebootpriority list in a storage location accessible by the processing device.5. The method of claim 1, wherein the operating system is loaded fromthe networked server without the processing device checking a rebootpriority list.
 6. The method of claim 1, wherein the operating system isloaded from the networked server without a user sending another commandduring a reboot process.
 7. A system comprising: an I/O device toreceive a command to load an operating system, wherein the operatingsystem to be loaded is a host operating system for a physical machine ora guest operating system for a virtual machine; and a processing device,coupled to the I/O device, to: determine whether the command includes aflag set to a network option; in response to a determination that thecommand includes the flag set to the network option, load the operatingsystem as the host operating system or the guest operating system from anetworked server; in response to a determination that the command doesnot include the flag set to the network option, load the operatingsystem from a location other than the networked server; and causerebooting to be performed according to the command with the use of theoperating system.
 8. The system of claim 7, wherein the processingdevice is to load the operating system from a location other than thenetworked server by: determining the location based on a reboot prioritylist.
 9. The system of claim 7, wherein the processing device is furtherto identify a network address of the networked server.
 10. The system ofclaim 7, wherein the processing device is further to: receive a rebootcommand that includes a reboot priority list; and store the rebootpriority list in a storage location accessible by the processing device.11. The system of claim 7, wherein the processing device is to load theoperating system from the networked server without checking a rebootpriority list.
 12. The system of claim 7, wherein the processing deviceis to load the operating system from the networked server without a usersending another command during a reboot process.
 13. A non-transitorycomputer readable storage medium including instructions that, whenexecuted by a processing device, cause the processing device to performa method comprising: receiving, by the processing device, a command toload an operating system, wherein the operating system to be loaded is ahost operating system for a physical machine or a guest operating systemfor a virtual machine; determining whether the command includes a flagset to a network option; in response to a determination that the commandincludes the flag set to the network option, loading the operatingsystem as the host operating system or the guest operating system from anetworked server; in response to a determination that the command doesnot include the flag set to the network option, loading the operatingsystem from a location other than the networked server; and causingrebooting to be performed according to the command with the use of theoperating system.
 14. The computer readable storage medium of claim 13,wherein loading the operating system from a location other than thenetworked server to the processing device comprises: determining thelocation based on a reboot priority list accessible by the processingsystem.
 15. The computer readable storage medium of claim 13, whereinloading the operating system comprises: identifying a network address ofthe networked server.
 16. The computer readable storage medium of claim13, wherein the method further comprises: receiving a reboot commandthat includes a reboot priority list; and storing the reboot prioritylist in a storage location accessible by the processing device.
 17. Thecomputer readable storage medium of claim 13, wherein the operatingsystem is loaded from the networked server without checking a rebootpriority list.
 18. The computer readable storage medium of claim 13,wherein the operating system is loaded from the networked server withouta user sending another command during a reboot process.